{ "BackgroundColor", "0:0:0" }, // background starts at black
{ "BoringModule", "YES" }, // yeah, we're a boring module
{ NULL, NULL }
};
NXRegisterDefaults (DEFAULTS_OWNER, FireflyDefaults); // register the defaults
}
@implementation FireflyView:View
/*
Here we do class initialization. All we do right now is set up our defaults.
*/
+ initialize
{
RegisterDefaults ();
return self;
}
/*
Here we're notified that our inspector has been installed. We use this for most of the initialization as we don't know of a better place; because of the way BackSpace does things, we're sure this will always get called before the screen saver module actually kicks in. Besides, we can't make our inspector reflect our configuration data before the inspector is loaded. If we already have some fireflies, everything must already be set up, so we don't worry about it.
Our first group of fireflies will just be wasted - never drawn. However, this is better than checking to make sure we don't release or draw non-existant fireflies every time we get a oneStep message.
[isBoringSwitch setState:(isBoring ? 1 : 0)]; // update the boring module switch on the inspector
fireflies = [self generateFireflies:fireflyCount]; // create some fireflies
}
[fireflyCountField selectText:self]; // select the firefly count so that we can quickly type to change it
return self;
}
/*
Here we make a single "move": create new fireflies, draw them, then erase the old fireflies. Erasing in the end provides the potential for erasing new fireflies, if they happen to fall in the same position as an old firefly, but this is minor, and it avoids the flicker caused by: bunch of fireflies, black, bunch of fireflies, black, etc. Erasing old fireflies individually is much slower than just blacking everything out, but if we blacked everything out, we would get flicker. Best would be to draw a single firefly, then erase the equivalent "old" firefly, but this is much slower due to the constant color changes. Maybe I should be doing this off screen, but I don't know that much yet.
*/
- oneStep
{
int firefly; // firefly counter
NXPoint * oldFireflies; // the old fireflies
int oldFireflyCount; // number of old fireflies
if (backgroundColorChanged) // background color changed; redraw the background
{
backgroundColor = [backgroundColorWell color]; // get new color
NXSetColor (backgroundColor); // set the color to redraw the background in
backgroundColorChanged = FALSE; // reset background changed flag
}
if (oldFireflies) // got old fireflies?
{
free (oldFireflies); // delete the old fireflies
}
return self;
}
/*
We're going to get a oneStep message in a second; don't bother to draw everything, but say that we have a new background color to ensure that we clear our drawing area.
*/
- drawSelf:(const NXRect *)rects :(int)rectCount
{
backgroundColorChanged = TRUE;
return self;
}
/*
Most of our initialization is actually done in the "inspectorInstalled" method - we assume that our inspector is always pulled up once (manually or by BackSpace) before we begin executing.
*/
- initFrame:(const NXRect *)frameRect
{
[super initFrame:frameRect];
[self allocateGState]; // For faster lock/unlockFocus
[self setClipping:NO]; // even faster...
srandom (time (0)); // seed random number generator
return self;
}
/*
Find our inspector panel and return it.
*/
- inspector:sender
{
char buf[MAXPATHLEN];
if (!sharedInspectorPanel) // inspector not loaded yet? do so now.
If we say we're boring, BackSpace won't call on us if it's in the "All" mode.
*/
- (BOOL)isBoringScreenSaver
{
return isBoring;
}
/*
Movement in the background color well - let's see if the color actually changed. If so, we note that it changed and write the new color to the defaults database. We don't actually set the new color; that's done in the "oneStep" method, or colors get confused.
Movement in the firefly color well - lets see if the color actually changed. If so, we set the new color and write the new color to the defaults database. We go ahead and set the new firefly color here as nothing gets confused when we do.
Movement in the firefly count field. If the new count is negative, reset the field, as negative numbers are invalid. Otherwise, if the new count is actually different from the old count, we note that fact and write the new value to the defaults database. We don't actually set the new count here or we risk not erasing old fireflies or erasing fireflies that didn't exist, tromping through memory we didn't allocate and happily grabbing non-existant (and often very strange) new fireflies. Kind of a bad thing, overall.
*/
- setFireflyCount:sender
{
char buf[256];
int tempCount;
tempCount = [sender intValue];
if (tempCount < 0) // don't allow negative number of fireflies
{
[sender setIntValue:fireflyCount];
}
else if (fireflyCount != tempCount) // the count really did change?
{
// we don't set the count here - that'll be done in "oneStep"
Reset the configuration settings to their defaults. A side benefit of the way I did this is that it cleans out the defaults database of values for this module, so someone removing the module from their system can easily remove all of the associated defaults. Here we remove all of the defaults, re-register the defaults, and re-read the defaults. We have to re-register our defaults or the act of looking one up causes a crash. (Guess how I learned about that...)
